Access Models

Imagine a world where your IAM platform not only understands the intricacies of your application data and how it works, but can also help you easily model role-based configuration for all applications within the access model. Permission Assist Access models understand the complexities of each application's permissions and help you define ideal access across all your applications. For example, you might create a Teller access model to define which applications tellers should have and which permissions they should have within each of those applications. Permission Assist makes this process easier, by analyzing your existing application data and providing recommendations.

Why Set Up Access Models?

Access models are commonly used to:

• See a detailed analysis and gain visibility into your application security models

  With access models, you can quickly and easily see a percentage of use for every permission within each application in the access model. Quickly see which permissions are most used, which permissions are the exception (where maybe only one or two people are assigned to a permission), and which permissions aren't used at all. You can also see who is and who isn't assigned to each permission.

• Model ideal access

  Within the Modeling tab, you can easily model ideal access without having to figure out which specific permissions belong to a group or what other permissions are affected when allowing access to a particular enlistment.

• Define an allowed set of permissions for reviews

  When access models are properly created, approved, and enabled, they can serve as a guideline for permissions the user is allowed to have. During a review, reviewers can have confidence in their decisions to approve or flag permissions by comparing a user's current permissions with the permissions they are allowed based on their enrolled access model.

• Define access for personnel events

  If you use the Operations module, Permission Assist will use the access models for personnel events such as onboarding, role transitions, and leaves of absence. For example, if one of your loan officers is getting promoted to Loan Manager, Permission Assist knows which permissions the loan officer currently has and which permissions need to be added, changed or removed as they transition to their new position. It can also help you manage a period of time where they may need access to both sets of permissions.

  If you don't use the Operations module, you can export access model permissions to help your team with personnel events.

 

To view the Access Models list, go the Manage menu on the main screen and select Access Models.

Column Button

The column button displayed in the top right corner of the page allows you to add or remove columns from the list. To change which columns are displayed, select the column button and then pick any of the following options.

Option	Description
Name	This option displays the Name column, which shows the name of the access model as defined on the Settings tab within the access model. It is selected by default and cannot be removed.
Description	Select this option to display the Description column, which provides a longer description for the access model as defined on the Settings tab within the access model.
Owner	Select this option to display the Owner column, which shows the owner assigned to the access model (defined on the Settings tab within the access model).
Count	Select this option to display the Count column, which shows the number of people enrolled in the access model, including disabled Identities.
Status	Select this option to display the Status column, which indicates whether the access model is enabled or disabled. An enabled access model can be used within reviews and can also be used for onboarding, role transitions, and leaves of absence.